command each time. If 'mystyle' is a format
that describes a popular program or is likely to be of use to others, you can
then share <filename>mystyle.style</filename> with other GPSBabel users.
-Send it along with a coherent descripton to the GPSBabel-misc mailing
+Send it along with a coherent description to the GPSBabel-misc mailing
list for consideration to be included in a future version.
</para>
</section>
<title>LAT_10EX / LON_10EX</title>
<para>
Defines the latitude or longitude in the format used i.e. by TomTom Navigator
- itinerary files. It is degress multiplied by 10 power X. X have to be replaced with
+ itinerary files. It is degrees multiplied by 10 power X. X have to be replaced with
a valid decimal value. A factor of 10000 would be generated by LAT_10E5 as shown
in the examples below.
</para>
<section id="style_def_pathcourse">
<title>PATH_COURSE</title>
<para>
- Course in degerees. Gpsbabel does not calculate this data by default;
+ Course in degrees. Gpsbabel does not calculate this data by default;
it is read from the input file if present. (If not present, it may be
calculated with the <link linkend="filter_track">track</link> filter.)
</para>
<listitem>
<para>Common format settings.</para>
<para> Any option from any of the formats listed here will be used by
- GPSBabel unless explictly provided on the command line.
+ GPSBabel unless explicitly provided on the command line.
</para>
</listitem>
<listitem>
As of this writing, <link linkend="fmt_garmin">Garmin's PVT
protocol</link> and
<link linkend="fmt_nmea">NMEA</link> are supported
- inputs. KML, NMEA, and the variou XCSV formats are supported on
+ inputs. KML, NMEA, and the various XCSV formats are supported on
output. Additional formats may be added by interested parties
later.
</para>
<para>
The complete list of available options to GPSBabel can be obtained by
running <command>gpsbabel -h</command>. While there are a number of
- options, most people will not use most of them, so don't be intimiated.
+ options, most people will not use most of them, so don't be intimidated.
</para>
<para><option>-p</option> Read preferences file. On startup, GPSBabel will look for a file named <filename>gpsbabel.ini</filename> containing preferences you have provided. This option lets you pick a different files. See <xref linkend="inifile"/> for more info.</para>
<para><option>-s</option> Write "smart" names. This option influences some - but not all - of our writers to try to build "smart" waypoint names. For example, in modules that know about geocaching, it may replace "GC1234" with the actual name of the geocache.</para>
<para>
This filter is used to "fix" unreliable GPS data by discarding points
that are believed to be unreliable. You may specify an
-HDOP and/or VDOP above a specified limit, a minimum number of satellits
+HDOP and/or VDOP above a specified limit, a minimum number of satellites
that must have been in view for a fix to be considered, or both.
</para>
<para>
</example>
</para>
<para>
-You may specify a minimmum number of satellites.
+You may specify a minimum number of satellites.
</para>
<para>
<example id="example_discard_filter_sats">
<para>
-This option specifies the minimum required number of satelites.
+This option specifies the minimum required number of satellites.
</para>
<para>
-This option, when used in connction with the wpt, rte, or trk options, tells
+This option, when used in connection with the wpt, rte, or trk options, tells
GPSBabel to delete the source data after conversion. This is most useful if
you are trying to avoid duplicated data in the output.
</para>
Timestamps are kept with the original waypoints so the
resulting track or route will have the interesting
characteristic that time runs backwards. This tends to make
- Magellan Mapsend, in particular, do a wierd thing and place
+ Magellan Mapsend, in particular, do a weird thing and place
each waypoint on a separate day.
</para>
<para> Additionally, if you're using this to reverse a route
gpsbabel -i gpx -f whatever.gpx -o bushnell -F /Volumes/Bushnell/WAYPOINT/whatever
</userinput>
will result in "whatever-0.wpt", "whatever-1.wpt", and "whatever-2.wpt" being
-credated in that directory.
+created in that directory.
Windows users may prefer the spelling:
<userinput>
gpsbabel -i gpx -f whatever.gpx -o bushnell -F e:/WAYPOINT/whatever
<para>
The basic information was found at <ulink url="http://mozoft.com/d3log.html">mozoft.com</ulink>.
In addition to the standard GPS track data of coordinates and timestamp, this format also stores the
- position fix and the number of satelites seen during recording.
+ position fix and the number of satellites seen during recording.
</para>
<para>
<productname>Destinator</productname> by
a unit number, with zero being the implied default. So if you
have three USB models on your system, they can be addressed as
<filename>usb:0</filename>, <filename>usb:1</filename>, and <filename>usb:2</filename>. To get a list of recognized devices,
- specifiy a negative number such as:
+ specify a negative number such as:
</para>
<para><userinput>gpsbabel -i garmin -f usb:-1</userinput></para>
</para>
<para>
The layout of GPI files isn't documented and our module was created
- via reverse engeneering. If you get a problem on reading or writing
+ via reverse engineering. If you get a problem on reading or writing
a GPI file, please provide that file (mailto:gpsbabel-misc@lists.sourceforge.net).
</para>
<para>
</para>
<para>
During the creation of an overlay file, a circle will be added to each
- postion of a waypoint or a route.
+ position of a waypoint or a route.
</para>
<para>
Sample layout of the ASCII overlay file
<programlisting format="linespecific">
[Symbol <number # >]
- Typ=<1=picture,2=Text, 3=line, 4=area, 5=retangle, 6=circle, 7=triangle>
+ Typ=<1=picture,2=Text, 3=line, 4=area, 5=rectangle, 6=circle, 7=triangle>
Group=<1=no group, number > 1=group number>
Col=<number of the line color>
Zoom=<1=no zoom, 2=zoom>
and is simply discarded while reading. If written, there will be a time_t value from the current (computed) timestamp.
</para>
<para>
-Somehwere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format. They are, in order, date (which eliminates most of the silliness above), an unknonw field, and a bearing. GPSBabel now reads the date and ignores the other two. We don't yet write these three fields for compatibility with earlier versions.
+Somewhere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format. They are, in order, date (which eliminates most of the silliness above), an unknown field, and a bearing. GPSBabel now reads the date and ignores the other two. We don't yet write these three fields for compatibility with earlier versions.
</para>
<para>
- <para>GpsDrive way.txt file format. A space seperated format
+ <para>GpsDrive way.txt file format. A space separated format
file. Tested against GpsDrive v 1.30 found at <ulink url="http://www.gpsdrive.de">gpsdrive.de</ulink>.
Contributed by Alan Curry.</para>
<para>Format used by GpsDrive to save tracks. Like GPSDRIVE a
-space seperated format file. See above for a link to GpsDrive.
+space separated format file. See above for a link to GpsDrive.
Contributed by Tobias Minich.</para>
compact flash cards. File formats were provided by Holux-Taiwan
<ulink url="http://www.holux.com.tw">holux.com</ulink> to the author.
The code was tested against version 2.27E1; other versions and
-receivers may work but have not been explictly tested. Anyone with
+receivers may work but have not been explicitly tested. Anyone with
information on other Holux receivers is encouraged to contact
jochen@bauerbahn.net.
</para>
<para> Comparing the waypoints of a .wpo files against other
formats like .gpx you may notice a small difference in the latitude
and longitude values. The reason is the low resolution of the
-coordinates in the wpo file format. In a .wpo file the reolution is
+coordinates in the wpo file format. In a .wpo file the resolution is
1/10"; in gpx for example it is 1/100". A a practical matter, this
loss is only about 1.7 meters (5 feet).
</para>
</para>
<para><userinput>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc</userinput></para>
<para>
-The same can be acheived by downloading directly from a barograph instrument
+The same can be achieved by downloading directly from a barograph instrument
supported by GPSBabel. For example with a Brauniger IQ Comp GPS variometer:
</para>
<para><userinput>gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</userinput></para>
</para>
<para>
<ulink url="http://www.magicmaps.de">MagicMaps</ulink> <productname>"Das interaktive Kartenwerk"</productname> is a Software from Germany. It's a
- route-planning software with a 3-dimensional envirounment.
+ route-planning software with a 3-dimensional environment.
</para>
<para>
The project files are XML based and we can read the main GPS items (names and coordinates).
<ulink url="http://earth.google.com">Google Earth</ulink>.
</para>
<para>There are concepts in KML that GPSBabel can't support very well on
-read becuase they don't map well into other programs. For example, KML has
+read because they don't map well into other programs. For example, KML has
ideas of camera views and names and descriptions can have arbitrarily
complicated HTML in them. KML files may have tiered "Styles" which
can identify sizing info and URLs of associated icons. Reading such
files with GPSBabel - even if your goal it to write it back out as KML - can often
-have suprising results. Simple files with waypoints and paths (which
+have surprising results. Simple files with waypoints and paths (which
GPSBabel represents internally as tracks) work fine.
</para>
<para>
In general, GPSBabel's KML writer is relatively strong. GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read.
</para>
<para>
- Google Earth 4.0 and later have a feature that can suprise users of this
+ Google Earth 4.0 and later have a feature that can surprise users of this
format. Earth's "time slider" feature controls what timestamped data
gets displayed. If you're using data that has timestampes (e.g. GPX
points that contain time or almost any track data) this will be important
</example>
<para>miniHomer has five POI called Home, <emphasis>Car</emphasis>, <emphasis>Boat</emphasis>, <emphasis>Heart</emphasis>, <emphasis>Bar</emphasis>. You can set the lla
-(Lattitude, Longitude, Altitude) for each of the POI. The format is
+(Latitude, Longitude, Altitude) for each of the POI. The format is
<emphasis><name>=<lat>:<lng>[:<alt>]</emphasis>
Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI.
</para>
<para>
- Tab seperated export-all (except geocaching data) file
+ Tab separated export-all (except geocaching data) file
format. Intended to serve as source for number-processing
applications like OpenOffice, Ploticus and others. Tab was chosen as
delimiter because it is a) supported by both OpenOffice and Ploticus
<para>
- When set to true, this places the "HINT:" entry from a geocacching.com
+ When set to true, this places the "HINT:" entry from a geocaching.com
pocket query at the end of the screen (scroll up for quick access) like
Cache Register and Topo7 do instead of at the top as Topo8 does.
</para>
<para>
- When set to true, this places the "HINT:" entry from a geocacching.com
+ When set to true, this places the "HINT:" entry from a geocaching.com
pocket query at the end of the screen (scroll up for quick access) like
Cache Register and Topo7 do instead of at the top as Topo8 does.
</para>
<para>
- When present on the command line and sending waypoins (either explicitly
+ When present on the command line and sending waypoints (either explicitly
via -w or as the default), this will erase
all waypoints in the receiver before sending the new ones.
</para>
-<para>This options gets the current longtitude and latitude from the attached GPS device
+<para>This options gets the current longitude and latitude from the attached GPS device
and returns it as a single waypoint for further processing. For example,
to return the current position from a USB Garmin to a KML file:
</para>
<para>
If this option is specified, GPSBabel will not read geocache placer information
-from a .loc file on input. That is, it will ignore any placeer names in the
+from a .loc file on input. That is, it will ignore any placer names in the
input file.
</para>
<para>
<para>
- Use ths option to set the title of the track.
+ Use this option to set the title of the track.
</para>
<para>
-This option is a boolean flag to specicy whether Google Earth should
+This option is a boolean flag to specify whether Google Earth should
draw lines from trackpoints to the ground. It defaults to '0', which
means no extrusion lines are drawn. The option of '1' is, of course,
most useful for points that aren't actually on the ground such as those
<para>
- The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data.
+ The deficon option is used to control the icon output when writing to this format. It overrides any icon information that might be present in the source data.
</para>
<para>
- The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data.
+ The deficon option is used to control the icon output when writing to this format. It overrides any icon information that might be present in the source data.
</para>
</para>
<para>
Please note that miniHomer by default uses 38400bps and does not autodetect the port speed. If you need autodetect, start as
-<userinput>gpsbabel -i miniHomer,initibaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx</userinput>
+<userinput>gpsbabel -i miniHomer,initbaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx</userinput>
</para>
By default GPSBabel creates only 'visible' items.
</para>
<para>
- Sample command to write an mmo file with 'in-vsisible' items:
+ Sample command to write an mmo file with 'invisible' items:
</para>
<para>
<userinput>
<para> Use this value as custom created_by value in an OSM file.</para>
<para>
-With this pption, the given string is added as the 'created_by' field in
+With this option, the given string is added as the 'created_by' field in
all the created nodes and ways.
</para>
<para>
- The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data.
+ The deficon option is used to control the icon output when writing to this format. It overrides any icon information that might be present in the source data.
</para>
<para>
- The deficon option is used to control the icon output when writing to this format. It overrides any icon informatino that might be present in the source data.
+ The deficon option is used to control the icon output when writing to this format. It overrides any icon information that might be present in the source data.
</para>
<para>
-genurl is a convenience option for generating the scaling paramaters
+genurl is a convenience option for generating the scaling parameters
when accessing the Tiger servers. It will output the latitude, longitude,
height, and width parameters in a form suitable for use in the URL to generate
a map that will hold all the points to be displayed and is suitably scaled
The margin may be specified in either decimal degrees or as a
percentage.</para>
<para>
-This option is most useful for ensuring there is adaequate space for
+This option is most useful for ensuring there is adequate space for
the label around the markers when generating automatically scaled maps.
</para>
<para>
When this option is enabled, we write an additional column called 'Filename'.
- The values of this column are filled with filenames of previos input formats.
+ The values of this column are filled with filenames of previous input formats.
</para>
<para>
This can be very helpful for locating specific waypoints (i.e. using the position filter)
<para> Garmin documents only PCX5, an older format limited to
the lame NMEA six-character waypoint names that's treated as a
-second-class citizien in current versions of MapSource. In Mapsource,
+second-class citizen in current versions of MapSource. In Mapsource,
use file->import to read these files. If you name the files *.wpt,
Mapsource will find them more easily.
</para>
This format provides support for XML flightplans from <ulink url="http://www.pocketfms.com">PocketFMS</ulink>.
</para>
<para>
- PocketFMS XML flightplans contain route and waypoint information and much more flight planning info as airspaces, aircraft performance, fuel managment etc. This format cannot be read by PocketFMS. Hence GPSBabel supports only input of route and waypoint information.
+ PocketFMS XML flightplans contain route and waypoint information and much more flight planning info as airspaces, aircraft performance, fuel management etc. This format cannot be read by PocketFMS. Hence GPSBabel supports only input of route and waypoint information.
</para>
<para>
The PocketFMS flightplan converter take into account the -w waypoint flag. If set then additional waypoints are stored to the route point and path information.
<para>This is a text format created by KuDaTa's PsiTrex program
for the Psion PDAs. The format can't be readily handled by XCSV, so
this format is handled explicitly. Waypoints, routes and tracks are
-all handled, with icon names used corresponding to verison 1.13 of
+all handled, with icon names used corresponding to version 1.13 of
PsiTrex. This module was contributed to GPSBabel by Mark
Bradley.</para>
</para>
<para>
Each kind of our basic GPS data (waypoints, routes, and tracks) is
- stored in a seperate file. Therefore you need three steps to
+ stored in a separate file. Therefore you need three steps to
convert a complex format like GPX or GDB into skyforce.
<userinput>
gpsbabel -i gpx -f file.gpx -o skyforce -w -F waypoints.txt -r -F routes.txt -t -F tracks.txt
This format supports the .sdf files from the Suunto product family
'Suunto Trek Manager', 'Suunto Ski Manager' and 'Suunto Sail Manager'.
The contents of the sdf file depends on the used product and can
- be one route or one track. Thatswhy when you want to use sdf on the
+ be one route or one track. Thats why when you want to use sdf on the
output side you have to use the
<link linkend="Route_And_Track_Modes">-r OR the -t</link> option. This will tell
GPSBabel which type of data should be written.
exported = Geocache export date
found = <link linkend="style_def_geofound">Geocache last found date</link>
fix = 3d, 2d, etc.
- gcid = Geocache chache id
+ gcid = Geocache cache id
geschw = Geschwindigkeit (speed)
hdop = Horizontal dilution of precision
head = Heading / Course true
<para>Read-only support for the csv file format used by <productname>Visiontac VGPS-900</productname> and <productname>Columbus V-900</productname> GPS data loggers. These seem to be two brand names for the exact same product.</para>
-<para>The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL chracters and fixed length fields, and therefore can not be handled by the normal csv module in GPSBabel.</para>
+<para>The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL characters and fixed length fields, and therefore can not be handled by the normal csv module in GPSBabel.</para>
<para>
<ulink url="http://www.visiontac.com/v900_specs.htm">Visiontac VGPS-900</ulink>
projects / gpsbabel.git / commitdiff